Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [platform-dev] Marking nested projects as derived, what are the risks?



On Wed, Jan 22, 2020 at 10:04 AM Andrey Loskutov <loskutov@xxxxxx> wrote:
I fully agree with Tom.
In one of the my answers I've already suggested to think about something like boolean IResource::isNested() API.

If we do that, then we need to change all clients to read this new state. I'm really looking for something that would work without having to rewrite a navigators and resource lists.
 
 Regarding isHidden() question: NO.
As javadoc on setHidden() says: Hidden resources are invisible to most clients.

The resource API does return those resources, so programmatically, they're visible.
What I'm unsure is what's meant by invisible and from which perspective. To my understanding, hiding is visual and it's a UI hint, it's exactly what I'm looking for then if I don't want folders for nested subprojects to leak in UI.


Back to the top