Skip to content

Conversation

@DimitarTachev
Copy link
Contributor

@DimitarTachev DimitarTachev commented Aug 14, 2018

PR Checklist

What is the current behavior?

We cannot start applications with a custom activity containing capital letters in their package names.

What is the new behavior?

We can start those applications.

Related to #3818

… letters in the package name e.g. org.myApp.MainActivity
@DimitarTachev
Copy link
Contributor Author

run ci

@Fatme
Copy link
Contributor

Fatme commented Aug 15, 2018

run ci

1 similar comment
@Fatme
Copy link
Contributor

Fatme commented Aug 15, 2018

run ci

@Fatme Fatme merged commit 6a63e61 into release Aug 15, 2018
@RoyiNamir
Copy link

RoyiNamir commented Aug 15, 2018

@DimitarTachev @Fatme @tsonevn
Hi.

I saw the fix with the new regex. . But still there is a subtle warning here.
You've fixed the capital matching in the REPEATING parts to be [a-zA-Z] - but you left the rule that the immediate NEXT LETTER should be capital.

In other words you still enforce this : *.*.[capital]*

The enforcement :

image

You can see it here :

Full match :

image

but if I change .M to .m then no match :

image

if it was delibirate , then fine. but if it wasnt , it should be changed.

This will prevent people from naming activities like org.app.nativescript ( looking at a lowercase- n)

@DimitarTachev
Copy link
Contributor Author

Hi @RoyiNamir,

Thanks for pointing into that. By convention, all Java classes should start with a capital letter. That's the reason for having this part of the regex just after the last dot. Its matching the activity class name.

@DimitarTachev DimitarTachev deleted the tachev/fix-app-start branch September 25, 2018 11:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants