Skip to content
This repository has been archived by the owner on Oct 25, 2023. It is now read-only.

Provide a configuration option for the location of the function #68

Open
andrew-su opened this issue May 16, 2022 · 2 comments
Open

Provide a configuration option for the location of the function #68

andrew-su opened this issue May 16, 2022 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@andrew-su
Copy link
Contributor

andrew-su commented May 16, 2022

Feature Request

A way to specify the location of a function within a directory. This is relevant to a monorepo consisting of multiple functions, possibly with multiple directories that could contain your function(s).

This could be something like BP_FUNCTION_SEARCH_PATH or BP_FUNCTION_PATH. We can discuss on what name is appropriate in the comments.

Describe alternatives you've considered

New repo per function and everything is top-level. Applications may have multiple moving parts that are closely related.

⚠️ Still in an early discovery phase

@andrew-su andrew-su changed the title Provide a configure the location of the function Provide a configuration option for the location of the function May 16, 2022
@bbtong
Copy link
Contributor

bbtong commented May 16, 2022

PB_FUNCTION_PATH seems acceptable to me.

@bbtong
Copy link
Contributor

bbtong commented Jun 27, 2022

Resolved by e88fe8a ?

nvm: They're separate work. This one relates to the situation where your functions are in different folders possible, so more of a directory level. The prior committed BP_FUNCTION just identifies the name of your singular default function.

@bbtong bbtong added the enhancement New feature or request label Jun 27, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants