Giter VIP home page Giter VIP logo

Comments (6)

tengstrand avatar tengstrand commented on August 16, 2024 2

Thank you for the kind words @marksto!

it becomes possible to support that a workspace is used more than once, but with different settings

This is an idea I currently have, which would allow you to override e.g. test configuration settings. Another option is that each workspace only specify the workspaces they use, within their own workspace.edn config. That is maybe a simpler solution, but may introduce code duplication. I will experiment with the different alternatives, and see what works best!

from polylith.

tengstrand avatar tengstrand commented on August 16, 2024 2

My current idea is that each workspace.edn will have a :workspaces key where you can specify workspaces that you share code from, e.g.:

{:top-namespace "backend"
 :interface-ns "interface"
 :default-profile-name "default"
 :compact-views #{}
 :vcs {:name "git"
       :auto-add false}
 :tag-patterns {:stable "stable-*"
                :release "v[0-9]*"}
 :projects {"development" {:alias "dev"}}
 :workspaces [{:alias "s"
               :path "../shared"}]}

This means that every workspace will be self contained when it comes to configuration, and we don't need an omnipotent configuration file at the root of the workspace, as we discussed in ClojureScript support.

from polylith.

marksto avatar marksto commented on August 16, 2024 1

Hi @tengstrand! Having this feature in Polylith will be awesome! I remember our discussion about this in Slack just a few months ago. The pace of recent developments is astonishing. Kudos to you, Sean, Furkan and Lee Read!

One quick question, if you don't mind. Could you, please, hint at how this sub-feature can be useful? What can it give?

it becomes possible to support that a workspace is used more than once, but with different settings

from polylith.

tengstrand avatar tengstrand commented on August 16, 2024 1

Yes, that's the idea.

from polylith.

marksto avatar marksto commented on August 16, 2024
:workspaces [{:alias "s"
              :path "../shared"}]

@tengstrand, hmm, so using relative paths for wss effectively means they also can successfully end up not being nested? I.e. having the following one-level file structure:

<root-dir>
- <ws-a> <— can reference bricks from b and c
- <ws-b> <— can reference bricks from a and c
- <ws-c> <— can reference bricks from a and b

from polylith.

avocade avatar avocade commented on August 16, 2024

👏🏻

from polylith.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.