Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ProtectedMethodInFinalClassCheck should be stricter #917

Closed
victornoel opened this issue Jul 28, 2018 · 26 comments
Closed

ProtectedMethodInFinalClassCheck should be stricter #917

victornoel opened this issue Jul 28, 2018 · 26 comments

Comments

@victornoel
Copy link

This is a follow-up on #901.

Basically, now that protected is accepted in final class when a method is an overriding one, it is possible for someone to override a default scoped method by making it protected in a final class.

This should be forbidden.

See #901 (comment) for some design considerations.

@0crat
Copy link
Collaborator

0crat commented Jul 28, 2018

@krzyk/z please, pay attention to this issue

@0crat
Copy link
Collaborator

0crat commented Jul 28, 2018

@victornoel/z this project will fix the problem faster if you donate a few dollars to it; just click here and pay via Stripe, it's very fast, convenient and appreciated; thanks a lot!

@krzyk
Copy link
Collaborator

krzyk commented Jul 28, 2018

@0crat in

@0crat 0crat added the scope label Jul 28, 2018
@0crat
Copy link
Collaborator

0crat commented Jul 28, 2018

@0crat in (here)

@krzyk Job #917 is now in scope, role is DEV

@0crat
Copy link
Collaborator

0crat commented Jul 28, 2018

Bug was reported, see §29: +15 point(s) just awarded to @victornoel/z

@0crat
Copy link
Collaborator

0crat commented Jul 28, 2018

@krzyk/z everybody who has role DEV is banned at #917; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Aug 2, 2018

@krzyk/z everybody who has role DEV is banned at #917; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Aug 7, 2018

@krzyk/z everybody who has role DEV is banned at #917; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Aug 12, 2018

@krzyk/z everybody who has role DEV is banned at #917; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Aug 17, 2018

@krzyk/z everybody who has role DEV is banned at #917; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Aug 22, 2018

@krzyk/z everybody who has role DEV is banned at #917; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Aug 27, 2018

@krzyk/z everybody who has role DEV is banned at #917; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Sep 2, 2018

@krzyk/z everybody who has role DEV is banned at #917; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Sep 7, 2018

@krzyk/z everybody who has role DEV is banned at #917; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0pdd
Copy link
Collaborator

0pdd commented Jan 24, 2019

@victornoel the puzzle #1006 is still not solved.

@paulodamaso
Copy link
Contributor

@victornoel Merged, please close.

@victornoel
Copy link
Author

@paulodamaso thx

@victornoel
Copy link
Author

@paulodamaso if I understand correctly, the bug is not fixed yet, we have to wait for #1006 now?

@paulodamaso
Copy link
Contributor

@victornoel Yes, I've break the task in two 30min tasks each: in #993 I've implemented the tests, and the rest will be made in #1006; PDD in action!

@0crat
Copy link
Collaborator

0crat commented Jan 24, 2019

@ypshenychka/z please review this job completed by @paulodamaso/z, as in §30; the job will be fully closed and all payments will be made when the quality review is completed

@0crat 0crat removed the scope label Jan 24, 2019
@0crat
Copy link
Collaborator

0crat commented Jan 24, 2019

The job #917 is now out of scope

@ypshenychka
Copy link

@0crat quality good

@0crat
Copy link
Collaborator

0crat commented Jan 24, 2019

@0crat quality good (here)

@ypshenychka The project doesn't have enough funds, can't make a payment

@0crat
Copy link
Collaborator

0crat commented Jan 24, 2019

Order was finished, quality is "good": +35 point(s) just awarded to @paulodamaso/z

@0crat
Copy link
Collaborator

0crat commented Jan 24, 2019

Quality review completed: +8 point(s) just awarded to @ypshenychka/z

@0pdd
Copy link
Collaborator

0pdd commented Feb 7, 2019

@victornoel the only puzzle #1006 is solved here.

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

No branches or pull requests

6 participants