How to use it in a monorepo with multiple languages ?

[slamer59]

Hi,
I wander how to setup my monorepo on this ?
I have folders like :

• apps :
  • python-app
  • js-app
  • ...
• libs

I see the config file is only one language ? Is there a workaround if no possibilities yet for multi language support ?

[MischaPanch]

See #492

[slamer59]

Thanks !
For the record :

• I would have think of multilanguage like this.

step-by-step, minimalist implementation plan for multi-language support

1. Update Project Configuration

• Example:

  project_name: my_project
  languages:
    - python
    - typescript
    - go

2. Create LanguageServerManager

• Implement a class with:
  • servers
  • server retrival
  • ...
    return server per file extension or smarter mechanism. it could be definied by a regex in config file

3. Update SerenaAgent
Direct call to language server -> get langauge server

4. Update Project Initialization
Init with language server manager instead of language server directly

• Tests / Docs ...

[ketema]

See #704 and #703
Plus my comment on #339

I have had a philosophical stance that AI Enhancement has led me towards:
The preference for simplicity historically stems from human cognitive limits, not architectural superiority.
With AI-enhanced workflows, robustness becomes more maintainable, not less.

This belief is what leads me to be confident in #703 even though it conflicts with this projects beliefs (Which I do respect). The beauty of forking is that both avenues are available.

[opcode81]

The preference for simplicity historically stems from human cognitive limits, not architectural superiority.

@ketema architectural superiority definitely results when a solution satisfies all requirements while being both easier to maintain and understand.
Whether AIs are better or worse at managing complexity does not matter. You will reach the threshold beyond which your software becomes unmaintainable at some point if you do not invest anything into clean design.
Implementing complex solutions to problems for which much simpler, more elegant solutions exist is never a good thing. Importantly, what is preventing the "simple" solution from being found is the fact that that it requires reasoning and deliberation; it is not always trivial to see the what the appropriate abstractions actually are. Introducing a new abstraction that render new requirements easy to implement can be far more powerful and maintainable than sticking with the abstractions one already has and "somehow getting it done". The latter, however, is usually what AIs will come up with - because they just aren't (yet) particularly good software designers.

With AI-enhanced workflows, robustness becomes more maintainable, not less.

Not sure what you are getting at. A robust design is typically a maintainable one, of course.

This belief is what leads me to be confident in #703 even though it conflicts with this projects beliefs

Can you name any concrete advantages of your solution?

[MischaPanch]

Serena now has full monorepo support, you just need to set the languages in your project.yml (see #704)

[opcode81]

We now added the possibility to dynamically add new languages via the dashboard: