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

Change doc_path doesn't work for me #263

Open
charly-palencia opened this issue Jul 12, 2014 · 4 comments
Open

Change doc_path doesn't work for me #263

charly-palencia opened this issue Jul 12, 2014 · 4 comments

Comments

@charly-palencia
Copy link

I tried that:

    Apipie.configure do |config|
       config.app_name                = "Adventours"
       config.api_base_url            = "/api/v1"
       config.doc_base_url            = "/apidocs"
       config.default_version         = "1.0"
       config.show_all_examples       = true
       config.validate                = false
       config.doc_path                = "docs/endpoints"
       # were is your API defined?
      config.api_controllers_matcher = "#{Rails.root}/app/controllers/api/v1/*.rb"
   end

User doc_path to change the /doc folder at configuration. but nothing change.

this is the right way, isnt it?

@saneshark
Copy link
Contributor

👍
I think I tracked down this issue to this line right here:

File.join(Rails.root,"doc","apipie_examples.json")

instead of 'doc', that should read something like: Apipie.configuration.doc_path

@saneshark
Copy link
Contributor

@iNecas which of the following other places that have the hardcoded doc path would require changes? See the query below:

https://github.com/Apipie/apipie-rails/search?utf8=%E2%9C%93&q=File.join%28Rails.root%2C%22doc%22

@iNecas
Copy link
Member

iNecas commented Apr 21, 2015

I would say all of the occurences would deserve extracting the value to a config method

saneshark added a commit to saneshark/apipie-rails that referenced this issue May 19, 2015
iNecas added a commit that referenced this issue May 28, 2015
@vindvaki
Copy link

Any word on this?

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

4 participants